A Series A SaaS founder walks into a board meeting with 14 months of cash left, according to her own spreadsheet. Three weeks later, her CFO reruns the numbers and finds the real figure is closer to 8 months. What happened? The founder's model divided current cash by last month's burn, a single data point, while new hires signed in the prior quarter hadn't fully hit payroll yet, and a large annual contract prepayment had temporarily inflated the bank balance. The runway wasn't 14 months long. It was 8. And in fundraising terms, that's the difference between raising on your own terms and raising in a panic.
This scenario repeats constantly across venture-backed companies, and it's rarely due to bad intentions. It's due to a runway calculation that's too simple to survive contact with how SaaS businesses actually spend and collect cash.
1. Why the "cash ÷ last month's burn" method fails
2. What a proper runway forecast actually models
3. Building an MRR-adjusted burn model step by step
4. A worked example for a Series A SaaS company
5. How VCs and CFOs stress-test runway before a raise
6. Common mistakes founders make
7. Industry best practices
8. Advanced considerations: cohort-based MRR, non-linear burn, growth capital timing
9. FAQs
Why the Traditional Approach Fails
The simplest runway formula looks like this: cash on hand divided by average monthly burn equals months of runway. It's fast, and it's almost always wrong in a way that matters.
Here's why. Monthly burn for a SaaS company isn't flat it changes as new hires ramp up, as sales and marketing spend scales ahead of revenue, and as revenue itself compounds through Monthly Recurring Revenue (MRR) growth. A single trailing-month snapshot captures none of that trajectory.
Now consider this: a company might have collected a large annual prepayment from a new enterprise customer, temporarily inflating its cash balance. A naive runway model would read that as an extra safety margin, when in reality that cash is already earmarked to be recognized as revenue and spent over the next twelve months.
What a Proper Runway Forecast Actually Models
Why does this matter more to a venture-backed company than a traditional business? Because fundraising itself takes time, typically 3-6 months from first pitch to wired funds, running out of runway mid-raise destroys negotiating leverage. Investors can smell desperation in a term sheet negotiation, and it shows up directly in valuation and terms.
The Core Components
- Starting cash balance, adjusted for any restricted cash or upcoming large one-time payments
- MRR growth rate, net of churn (Net MRR growth)
- Gross margin, since not all recognized revenue is cash-equivalent contribution
- Payroll burn, including new hire start dates and ramp-up time to full productivity
- Non-payroll operating expenses (software, infrastructure, office, professional fees)
- One-time or lumpy cash events (annual prepayments, tax payments, equipment purchases)
Building the Model Step by Step
Let's model a Series A SaaS company with 25,000 USD in current MRR, 8% monthly gross MRR growth, 3% monthly churn, and 900,000 USD in the bank.
Step 1: Calculate net MRR growth rate.
Net MRR Growth = 8% − 3% = 5% per month
Step 2: Project MRR forward. Starting at 25,000 USD and compounding at 5% monthly:
| Month | Projected MRR (USD) |
|---|---|
| 1 | 25,000 |
| 3 | 27,563 |
| 6 | 32,120 |
| 9 | 37,442 |
| 12 | 43,653 |
Step 3: Convert MRR to cash contribution. At a typical SaaS gross margin of 75%, monthly cash-equivalent contribution from revenue is MRR × 0.75.
Step 4: Project monthly burn. Assume the current total monthly operating cost is 130,000 USD, growing to 150,000 USD by month 6 as two new hires ramp to full salary, and staying flat afterward, a common pattern following a hiring freeze post-raise.
| Month | Revenue Contribution | Operating Cost | Net Burn | Cash Balance |
|---|---|---|---|---|
| 1 | 18,750 | 130,000 | (111,250) | 788,750 |
| 3 | 20,672 | 140,000 | (119,328) | 555,000 (approx.) |
| 6 | 24,090 | 150,000 | (125,910) | 170,000 (approx.) |
| 7 | 25,300 | 150,000 | (124,700) | 45,000 (approx.) |
The result? This company's true runway is approximately 7 months, not the 900,000 ÷ 130,000 ≈ 6.9 months a naive flat-burn model would coincidentally arrive at here, but in most real scenarios where hiring accelerates burn mid-year, the naive model overstates runway significantly, sometimes by 2-4 months.
How VCs and CFOs Stress-Test Runway Before a Raise
Investors rarely take a single-scenario runway forecast at face value. They typically ask for three cases side by side:
| Scenario | MRR Growth Assumption | Typical Use |
|---|---|---|
| Base Case | Current trailing 3-month average growth rate | Default planning scenario |
| Downside Case | 50% of base case growth, churn +2 points | Tests resilience if growth slows |
| Upside Case | Base case + 30%, reflecting a successful new channel | Used to justify a larger raise size |
A founder who walks into a fundraise with only the upside case is, frankly, going to get challenged hard in diligence. The stronger move is to lead with the downside case and show the company still survives 9-12 months even under pressure that builds credibility fast.
Common Mistakes to Avoid
- Using a single trailing month's burn rate instead of a forward-looking, ramp-adjusted projection
- Ignoring new hire ramp time, assuming full productivity and full cost from day one
- Treating annual prepayments as available cash rather than deferred revenue already earmarked for delivery costs
- Forgetting gross margin assuming 100% of MRR is cash-equivalent contribution
- Failing to model a downside churn scenario before approaching investors
- Confusing runway with "months until zero" instead of "months until minimum operating cash threshold," which should include a safety buffer
Industry Best Practices
Most experienced SaaS CFOs update the runway model monthly, not quarterly, and tie it directly to the actual general ledger rather than a static spreadsheet built once after the last raise. They also build in a minimum cash threshold, often 2-3 months of buffer, rather than modeling all the way to a literal zero balance, since operational reality (collections delays, unexpected expenses) rarely allows spending down to the last dollar.
Advanced Considerations
Cohort-Based MRR Modeling
Rather than applying a single blended churn rate, mature SaaS finance teams model MRR by customer cohort since early cohorts typically churn at different rates than recent ones, and enterprise customers churn far less than SMB customers. Blending these into one rate can mask a serious retention problem in a specific segment.
Non-Linear Burn Events
Annual insurance renewals, cloud infrastructure reserved-instance payments, and year-end bonuses create burn spikes that a smooth monthly average will miss entirely. These should be modeled as discrete line items in the specific month they occur.
Growth Capital Timing
For companies raising growth-stage capital rather than early venture rounds, runway modeling should also incorporate debt facility covenants and minimum liquidity requirements, which can restrict how low the cash balance is legally allowed to fall well above the point where the operating business would otherwise still be viable.
Frequently Asked Questions
What's a safe minimum runway before starting a fundraise?
Most investors and experienced operators recommend starting the process with 9-12 months of runway remaining, since the process itself typically takes 3-6 months and often runs longer than planned.
Should runway be calculated on gross burn or net burn?
Net burn (cash out minus cash in from revenue) gives the true monthly cash decline and is the number that should drive the runway calculation. Gross burn is useful separately for understanding cost structure.
How much buffer should be built into a runway model?
A common approach is to model down to a minimum operating threshold of 2-3 months of expenses, rather than to a literal zero cash balance, to account for collection delays and unplanned costs.
Does annual prepaid revenue improve runway?
It improves the cash balance temporarily, but since that revenue is typically recognized and the associated delivery costs incurred over the contract term, it should not be treated as free, spendable cash in a runway model.
Conclusion: What to Do Next
Before your next board meeting or fundraising conversation, rebuild your runway model with monthly granularity, ramp-adjusted headcount costs, and a realistic downside churn scenario. Present the downside case first it's the fastest way to earn credibility with investors who have seen too many overly optimistic decks. And start the fundraising clock at 9-12 months of runway, not 6, because the real risk was never running out of cash. It was running out of time to rise before you did.
0 Comments